**************************************************************************
(C) COPYRIGHT International Business Machines Corporation 1994, 1999
    All Rights Reserved. Licensed Materials - Property of IBM.
**************************************************************************
FILE: README FOR MSS V2.1 PTF 3


The IBM Multiprotocol Switched Services Configuration Program
V1 R2.1 PTF 3 is a replacement for IBM Multiprotocol Switched Services 
Configuration Program V1 R2.1.

The Nways Multiprotocol Access Services Configuration Program User's
Guide is available separately (GC30-3830).
 
 
 Table of Contents:

	1.  Installation
        2.  Restrictions
	3.  Migration 
        4.  Problems fixed in this Configuration Program 
        
    
1. INSTALLATION

 Obtaining the Configuration Program Electronically

  Steps to obtain the Configuration Program electronically:
   
   You can obtain the Configuration Program electronically, from
   http://www.networking.ibm.com/support/code.nsf/8210code
   
 Steps to obtain the Configuration Program electronically:
   
     1. From the URL above, select  MSS Server Config Tool Version 2.1 PTF3.
     2. Select from Files in the Package at the bottom of the screen to download 
        the files.  
   
  
   DISKETTE images
   
      1. Format 6 diskettes 
      2. From Windows or OS/2, download the six self-extracting files
         in the package to your harddisk.
      3. Run the first file and follow the instructions to create the first
         diskette.
      4. Repeat step 3 until you create all the six diskettes from running
         the downloaded files.
      5. Place the first diskette onto the diskette drive 
      6. Proceed to the steps in Installation from Diskettes. 


 Installation From Diskettes

  AIX 
       1. Type   dosread -a INSTALL.AIX INSTALL.AIX  and press ENTER
       2. Change the file permission
           Type  chmod 550 INSTALL.AIX and press ENTER
       3. Type INSTALL.AIX  press  ENTER
	     Follow the prompts that appear on the screen to complete
             the installation.
     

  OS/2
       1. Type A:os2inst and press ENTER     
          Follow the prompts that appear on the screen to complete
          the installation

  WINDOWS '95
       1. From the Start Menu,select Run
       2. Type A:\install and press ENTER

  WINDOWS
       1. From the FILE menu, select Run
       2. Type A:Install and press ENTER
       
  
       TLV definitions are written to the file cfg.tlv in the configuration
program installation directory.  Do NOT delete this file if you are
re-installing the configuration program.  In order to successfully
use existing configurations stored in a cdb file that have user defined TLVs
configured in an ELAN definition, the cfg.tlv file containing these TLV 
definitions is required.  If you are installing the configuration program in 
a new directory, copy the cfg.tlv file to the new directory before starting 
the configuration program.  To verify that no TLV information is missing, 
review entries on the TLV Definitions page for each ELAN.
   
       OS/2 Warp Version 4 is not supported. 
   
2. RESTRICTIONS
    
   This section discusses some KEY considerations that users must be aware 
   of:

   Windows environment:

      If TCP/IP is not installed and RUNNING before using the "Send Single"
and/or "Send Multiple" functions the Configuration Program will hang.

   OS/2 environment:
  
      A selection of 65535 colors when using OS/2 WARP will prevent the
program bitmap from being displayed.

 ELS (Event Logging System) data:
    
      The Configuration Program does not support ELS configurations. Thus, if 
you want to configure ELS you must use the command line interface on the
server. If ELS configurations are included in a configuration file that you
retrieve from a server, the ELS configurations will be saved and restored 
to the server when you send the configuration back to the server.  Any changes
to the ELS configurations made on the server after retrieving the 
configuration and before sending it back will be lost.  

 COMMAND LINE

      If you are using the command line interface to configure your box,
you cannot use a '*' in the command.  

3. MIGRATION SUPPORT FOR DOWNLEVEL CONFIGURATION FILES

  
  To use configuration files created by earlier versions of
  the configuration program, you MUST migrate to the new
  release format. If the only copy of the configuration is
  either in the MSS or in binary format, you must use
  the version of the configuration program that created the
  configuration to create the configuration database file
  and then use the configuration program to migrate that
  database file.
 
 Creating Configuration Database File
  To create the configuration database file:
  1.  Start the previous version of the configuration program.
  2.  Select READ CONFIGURATION to read the existing
      configuration into the configuration program. Another
      way to load an existing configuration into the
      program is to select COMMUNICATION, SINGLE, and then
      RETRIEVE from the Configuration menu.
  3.  Select SAVE CONFIGURATION from the File menu.
  4.  Save the configuration into a file with file extension .CDB.
 
 Converting a Configuration Database File
  Configurations in a configuration database may be
  migrated to the new release format by:
  1.  Starting the current version of the configuration program.
  2.  Selecting OPEN CONFIGURATION from the File menu.
      Select the old configuration from within the .cdb
      file you created in "Creating Configuration Database
      File." The configuration program will then ask if you
      wish to convert the configuration to the new format.
  3.  Selecting SAVE CONFIGURATION AS to save the configuration
      to a new file with a new name. Using the "Save configuration
      as" function allows you to keep the existing configuration
     file for future use.

  NHRP auto-configure
    
  After migration of the configuration database file to to MSS V1R2.1
  is completed, if no NHRP functions were previously configured, NHRP at
  the box level will be defaulted to 'enabled'. As a result of this,
  each ATM interface will have a corresponding NHRP interface associated
  with it.


4.  APARS (Problems) fixed in this Configuration Programs  

    IR39318  -   Config Tool changes LES/BUS from ATM 0 to ATM 1 upon reading
    IR39388  -   Remore LESs lost upon reading
    IR39774  -   Config Tool should limit LEC ATM Address Selector.
    NA05020  -   ARP Server is not required when running CIP over VPI/VCI.